releases: fix the validate_password.enable links in the v6.5.0 release notes (#24197) - #24255

This is an automated cherry-pick of #24197

What is changed, added or deleted? (Required)

In the v6.5.0 release notes, the system variables table links validate_password.enable to #password_reuse_interval-new-in-v650 in three rows (validate_password.number_count, validate_password.policy, and validate_password.special_char_count). That anchor belongs to a different variable, so readers land on the password_reuse_interval section. The other five links to validate_password.enable in the same table already use #validate_passwordenable-new-in-v650. This PR changes the three links to that anchor.

This was found while reviewing the Japanese translation (#24158), which mirrors the EN text. This PR targets release-8.5 so that the weekly EN→JA sync carries the fix to the Japanese docs.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v8.5 (TiDB 8.5 versions)
• v8.4 (TiDB 8.4 versions)
• v8.3 (TiDB 8.3 versions)
• v8.2 (TiDB 8.2 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Corrected the links in password-policy setting descriptions so they point to the relevant enablement setting.